home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Grand Slam 3
/
Grand Slam 3.iso
/
004
/
!11wall.arj
/
SYSOP.DOC
< prev
next >
Wrap
Text File
|
1995-04-29
|
12KB
|
283 lines
- Another Brick In The Wall -
Sysop Documentation
Most BBSes today feature some sort of graffiti wall or oneliner door. They
provide a great outlet for short bursts of communication between callers, and
facilitate the posting of material often too brief for the message bases;
unfortunately, many of the graffiti wall doors available are lacking on the
Sysop end of things, and provide few extra features. Another Brick In The Wall
was written to address this problem. Users of The Wall will enjoy its power
and ease of use, while Sysops will enjoy its flexibility and control.
- Features -
o Assembly language serial I/O
o Supports speeds up to 115.2k and 16550 UARTs
o Internal ANSI emulation
o Multitasker aware (DESQview, Windows, OS/2)
o FOSSIL support (FOSSIL not required however)
o Split-screen chat with word wrap
o Multi-node compatible
- Running The Wall -
The syntax for executing WALL.EXE is: WALL <config file> [local] [sysop] [...]
The config file is a 7-line text file:
Line 1: Dropfile type [RA,WC2,WC3,SF,CL]
Line 2: Dropfile path/name
Line 3: BBS name
Line 4: Sysop first name
Line 5: Sysop last name
Line 6: COM port interrupt [1-7, 0 for FOSSIL]
Line 7: Use error log? [TRUE/FALSE]
Included is the utility MAKECFG.EXE, which will request this information and
create a configuration file:
Name of config file to be created? Name the file. Ex: WALL.CFG.
Dropfile type? Enter one of the following codes: RA - DORINFO.DEF
WC2 - CALLINFO.BBS
WC3 - DOOR.SYS
SF - SFDOORS.DAT
CL - use command line
Path/name of dropfile? Where the previously designated dropfile is created.
BBS name? Self-explanatory.
Sysop name? Self-explanatory.
COM port interrupt? The interrupt of the COM port given in the dropfile.
Valid interrupts are values 1-7. Enter 0 to use FOSSIL.
(Note that this is asking for the INTERRUPT number, not
the COM port number.)
If you are unsure of what this value should be, here
are the typical interrupts:
COM1 - IRQ4
COM2 - IRQ3
COM3 - IRQ4
COM4 - IRQ3
Log errors? Enter TRUE to write all errors encountered to a log. Enter
FALSE to not log errors.
Here is a sample config file:
WC3
C:\RA\DOOR.SYS
Temples of Syrinx
Scott
Stuart
3
FALSE
If your software cannot create a dropfile compatible with one of the above
formats, then you must specify type CL, and run The Wall with command line
parameters:
WALL <config file> <ANSI/1/GR/COLOR/TRUE> <baud> <ufirst> <ulast> <comport>
| | | | |
| | | | |-COM port #
| | | |
| | | |-User's last name
| | |
| | |-User's first name
| |
| |-Baud rate (300-115200. 0 = Local)
|
|-Any of these will specify ANSI on, otherwise ANSI is off.
However, The Wall forces ANSI color so this value is non-
consequential.
The Wall must be run from the directory in which all its files are located; it
is recommended you run The Wall from a batch file such as this:
@ECHO OFF
C:
CD \WALL
WALL.EXE WALL.CFG
To run The Wall locally from the command line, add the parameter LOCAL.
- Other Command Line Options -
The following parameters can also be added to fine-tune the appearance and
behavior of your Wall:
MAX=x Sets the maximum number of lines the wall will hold (x is a number
from 1-65535). Once x lines are on the wall, the oldest graffiti
will be removed as new lines are added. If no limit is specified,
the size of the wall is unlimited.
RANDOM When the wall is viewed, places the lines of graffiti randomly.
Normally, the graffiti is shown exactly how it is written (usually
left-justified), but with this parameter the graffiti is aligned
randomly.
CENTER When the wall is viewed, centers each line of graffiti.
LINES Separates each line of graffiti on the wall with a line.
OLDCTL The Wall now uses the numeric keypad arrow keys to change colors while
entering graffiti; however, the controls from v1.0 are still
recognized and may be continued to be used by those who prefer them.
Use this parameter to display the old control options to the user
rather than the new ones.
- Writing on The Wall -
Writing on the wall is extremely simple. After a user has selected "W", he is
prompted for a line of text, and given the option to hit TAB to change colors,
or ESC to randomize text color. Hitting TAB allows the user to change the
foreground color, background color, and blink attribute. These things are
easily changed via the numeric keypad; please note that to use the arrow keys
the Num Lock must be on.
Hitting ESC causes each subsequently typed letter to have a different foreground
color, and this will continue until the user presses ESC again or changes the
colors manually via TAB. The Wall will not allow text to have the same
foreground/background color, and will not save empty entries.
The Wall's flexible color options will provide you and your users with a
vivid and exciting wall.
- Profanity Filter -
The Wall allows the Sysop to define a list of words or phrases not allowed to
appear on the wall. To do this, simply place all undesirable words/phrases,
one per line, in a text file named CENSOR.LST; if a user attempts to enter a
line of graffiti containing one or more words in this list, he will be
notified that his message is not appropriate and the line will not be placed
on the wall. For a whole-word filter (i.e., filter "ass" but not "assume"),
put spaces or underscores around the word in CENSOR.LST (i.e., "_ass_").
- Sysop Functions -
To access The Wall's Sysop functions, view it using the (S)ysop Wall View
option. When the wall is viewed like this, a status bar appears above each
line, showing who wrote it and when. The prompt also contains three
additional options available only to Sysops:
[T]runcate Truncates the wall at the specified line number. All entries
below the specified number are deleted. (To delete the wall
entirely, either truncate at #1 then delete #1, or go to DOS
and delete the file WALL.DAT.)
[D]elete Removes the specified line from the wall.
[R]eprimand Some users like to take advantage of the anonymity of graffiti
walls and write offensive things. This is not a problem with
The Wall; not only can the Sysop easily find out the author of
any line of graffiti, but this handy feature allows for
automatic reprimanding of such users. The user who posted the
graffiti corresponding to the specified line number will
receive a reprimand the next time he enters The Wall; try one
on yourself to see exactly what it does. Although this is not
a replacement for direct Sysop intervention, it is a convenient
way to handle users who may get a little out of hand.
Anyone using The Wall locally has access to these Sysop functions, and remote
users can also be granted this access via inclusion in the SYSOP.LST file.
As with the profanity filter file, create a text file containing the names of
those users whom you wish to have access to Sysop Wall View, with one name
per line. The name must match up exactly, or no extended access is given.
Whether local or remote, the Sysop defined in the config file always has
access to Sysop functions.
- Multinode Usage -
The Wall does not currently support simultaneous multinode usage. If a user
attempts to enter The Wall while it is already in use, he will be informed of
this and brought back to the BBS.
In the event of a system crash while The Wall is in use, the door will not be
able to clean up as usual; an abrupt termination of the door will cause
the WALL.USE semaphore to not be deleted, thus preventing anyone from entering
the door. Please be sure to delete this manually in such a situation.
- Sysop Keys -
While a user is in The Wall, the following functions are available to the
local Sysop:
[F1] - Toggles status/help display.
[F2] - Activates chat mode. Hit ESC to exit chat.
[F3] - Drops the local end to DOS, and displays an appropriate message
to the user.
[F4] - Kicks the user out of the door and back to the BBS.
[F10] - Kicks the user out of the door and drops carrier.
- Support -
Support can be obtained by either calling the support BBS, sending NetMail,
or Internet EMail to sstuart@crow.cybercom.com. See the section below on
registering for info on the support BBS. Comments, suggestions, and bug
reports welcome!
- Registering The Wall -
In the unregistered version of The Wall, MAX=10 is forced, and there's an
unseemly delay upon exit. However, these annoyances can be eliminated by
registering, which costs only five dollars. Please register!
Registration entitles you to free minor and major upgrades. To register The
Wall, print out REGISTER.TXT and send it to the address listed. If your BBS
is a member of FidoNet, your registration key will be conveniently sent to
you. If not, you can call the Wall support BBS to download it:
Temples of Syrinx
908/914-9807
FidoNet 1:107/751
RemoteAccess v2.02+
USR Courier HST V.34
Logon using the exact name and password specified on the order form, and
your registered Wall will be waiting as an EMail file attach.
To use your registration key, simply place it in the directory with all the
other Wall files and rename it to WALL.KEY.
The latest version of The Wall is available on Temples of Syrinx; it can be
obtained by calling the board and downloading it, or FREQing the magic name
"WALL".
And if you don't already have it, FREQ "SAD" to get Search and Destroy, the
popular Battleship-style door game by Scott Stuart.
- Special Thanks -
Alpha Testing Team: Dave Back Beta Testing Sites: Bugman BBS
Matt Edelhauser Sysop - Steve Mack
Paul Tricoli 908/506-9492
Paul's Boutique
Sysop - Paul Tricoli
609/PRI-VATE
The Wall was written using URDoor comm routines (c) 1995 Kenneth Bledsoe.
Another Brick In The Wall online graffiti wall door (c) 1995 Scott Stuart.
Distribution of Another Brick In The Wall is permissible and encouraged,
providing that no fee be assessed for its distribution other than any normal
fee that may be associated with the medium by which it is distributed. The
Wall must be distributed in its original archive form, unaltered and with no
registration keys.